投稿時間:2023-08-14 08:11:17 RSSフィード2023-08-14 08:00 分まとめ(14件)

カテゴリー等	サイト名等	記事タイトル・トレンドワード等	リンクURL	頻出ワード・要約等/検索ボリューム	登録日
js	JavaScriptタグが付けられた新着投稿 - Qiita	NeosVR コンパイラ その4	https://qiita.com/ohisama@github/items/160d4be68af79e2ccf6f	usefrooxengine	2023-08-14 07:07:00
AWS	AWSタグが付けられた新着投稿 - Qiita	vCenter Converter で EC2 インスタンスを VMware Cloud on AWS に移行する（VTGW編）	https://qiita.com/mtoyoda/items/10e788729af6564b03a7	vcenterconverter	2023-08-14 07:18:44
Docker	dockerタグが付けられた新着投稿 - Qiita	vector.devで`host_metrics`のhostフィールドを環境変数で上書き指定する	https://qiita.com/takiuchi/items/1ae33c8dbba12a6af7f8	dockerampvect	2023-08-14 07:09:14
海外TECH	DEV Community	Learn Vue: List and Conditional Rendering.	https://dev.to/kingowisdom/learn-vue-list-and-conditional-rendering-203j	Learn Vue List and Conditional Rendering Imaging you are developing an application and you want to render some data in the browser based on certain conditions or you have an array of data that you want to loop through and display to in the browser how can we achieve this Vue In this guide we we ll learn List rendering and conditional rendering in Vue and how we can tap into the powers of the v if and the v for directives List RenderingThe v for directive is used to render an array of items or an object The syntax is very simple and easy item in items where item is the individual item that would be rendered and items is the list we are looping through Rendering array with v for template lt div v for name in names gt name lt div gt scriptconst names ref Vue Nuxt Vite Vitepress v for will loop through the names array and display each of name in the browser Rendering object with v forThe v for can also be used to iterate through an object the sequence of the iterations will rely on the outcome of invoking Object keys on the object template lt ul gt lt li v for value in myObject gt value lt li gt lt ul gt scriptconst myObject reactive title How to render lists in Vue author KingstonCodes publishedAt Optionally we can also include the key of each property in the object lt li v for value key in myObject gt value lt li gt v for and keyIn order to maintain the state of the items when rendering them to the browser we can introduce a unique key attribute to reference to each item in the list lt div v for item in items key item id gt item lt div gt The v for directive is extremely important as it helps us render lists to the browser effortlessly Conditional RenderingWe can render anything to the browser conditionally using either the v show directive or the v if directive Both v show and v if can be used to achieve the same result the difference is that the v show directive only toggles the CSS display property of the element hence an element with the v show directive will always be present in the browser v showLet s see an example of conditional rendering with the v show directive lt div v show isTrue gt content here lt div gt scriptconst isTrue ref true The div will always be rendered in the browser as long as isTrue remains true likewise when isTrue is false the div disappears from the browser v ifLike the v show directive the v if directive is also used to conditional render elements to the browser the element is only rendered when the directive s expression returns a truthy value lt div v if isTrue gt content here lt div gt scriptconst isTrue ref true Another difference between the v if directive and the v show directive is that we can use v else and v else if directives to match cases where the directives expression isn t true v if with v else and v else if lt div v if isTrue lt gt display content here lt div gt lt div v else if isTrue gt gt display content here lt div gt lt div v else gt display content here lt div gt scriptconst isTrue ref Like the traditional if else if and else in JavaScript the v if v else and v else if can be used to achieve similar result In the above example the v else block will run because isTrue is neither less than or greater than zero Similarly the v if block or v else if block will run depending on whether isTrue is greater than or less than v for with v ifSometimes we might want to render a list to the browser when certain conditions are met to achieve this we need to first loop through the list with v for then check whether the condition is met with v if before displaying it The problem is it is not a good practice to use the v for and v if directives on the same element because when they exist on the same element v if will have higher level of priority over v for meaning that v if will not be able to access the variable from the v for block lt This will not work gt lt li v for todo in todos v if todo isComplete gt todo name lt li gt To fix this let s move the v for directive to a wrapper tag lt template v for todo in todos gt lt li v if todo isComplete gt todo name lt li gt lt template gt And that s it the v for block will always execute before the v if block thereby allowing the v if directive access to the v for variable and carry out the action	2023-08-13 22:34:35
海外TECH	DEV Community	Injecting Micro-Frontend CSS in single-spa	https://dev.to/webjose/injecting-micro-frontend-css-in-single-spa-oe8	Injecting Micro Frontend CSS in single spaOnce more we gather together around the fascinating topic of making Vite projects work with single spa Today s topic is most likely a very awaited one How does one inject a micro frontend s CSS into the page that loads it By the way note that this question is not Vite specific but because this series is about working with all Vite projects we will explore the topic around what Vite can provide Let s start where we left off in the previous article shall we Modifying the mySspaRoot ProjectI don t know if you noticed but during our exercise in the previous article we saw a decently styled React micro frontend coming up in our root project s HTML page while said micro frontend was being served npm run dev This might be a coincidence Since both projects are Vite lt Technology gt projects they are very similarly styled including CSS class names In order to make the CSS effort evident we ll modify the root project enough to break this similarity at least enough to makes us realize if some styling was a coincidence or not This will help us see the extent of the effort we need to take into making CSS work for us First and foremost I changed the page styles by simplifying src style css significantly I also removed the button styling because as seen later I removed the counter button from this root project Enough said This is how my src style css file looks like now root font family Inter system ui Avenir Helvetica Arial sans serif line height font weight color black background color ffffff font synthesis none text rendering optimizeLegibility webkit font smoothing antialiased moz osx font smoothing grayscale webkit text size adjust body margin display flex place items center min width px min height vh h font size em line height app margin auto padding rem text align center Most fancy styling that I don t even know about was removed maximum document width was taken out as well I m using K monitors so The HelloWorld Vue component was deleted entirely it contained the counter button and the contents of src App vue were changed to this lt script setup lang ts gt import vueLogo from assets vue svg import Link from components Link vue lt script gt lt template gt lt main gt lt section gt lt img src vite svg class logo alt Vite logo gt lt h gt lt img src vueLogo alt Vue class vue gt Root Project lt h gt lt h gt vite plugin single spa lt h gt lt div class content gt lt p gt Welcome to the development of lt em gt vite plugin single spa lt em gt This is content provided by the root project and comes from the lt em gt App lt em gt Vue component lt p gt lt Link url mifea gt Load Microfrontend A lt Link gt lt div gt lt section gt lt section id single spa application mifeA gt lt section gt lt main gt lt template gt lt style scoped gt main display flex place items left gap em main gt section max width border rgb em dashed border radius em padding em main gt section first child border none color white background color rgb main gt section first child a main gt section first child a visited color yellowgreen h h h margin padding div content text align justify p em color yellow font weight bold logo height em padding em will change filter transition filter ms logo hover filter drop shadow em bafeaa vue height em lt style gt The net result One more detail The hyperlink at the bottom that triggers loading the micro frontend is a component named Link that I created very quickly using single spa s navigateToUrl function This is components Link vue lt script setup lang ts gt import navigateToUrl from single spa defineProps lt url string gt lt script gt lt template gt lt a href url click prevent navigateToUrl url gt lt slot gt lt slot gt lt a gt lt template gt With these modifications we can start essaying solutions Initial TestingAs per usual we will test with vite serve npm run dev and vite preview npm run build npm run preview We will determine what work is needed for each command in the CSS arena Let s start with vite serve Run the root project using npm run dev and then run the React micro frontend also using npm run dev Now click the hyperlink to load micro frontend A This is what you probably see Let s compare it to the standalone version of the react micro frontend Load http localhost Remember that our projects behave dually while in serve mode so we don t have to do anything other than enjoy this duality This is what you should see Now let s compare The React logo is missing This is no surprise Until the Vite development team agrees to modify how Vite handles the base property we won t have assets showing up in our root project while in serve mode The button is not styled If you are observant I intentionally changed the hover color of the Vite logo in the root project to see if the Vite logo in the React side inherited it This did not happen Pretty good I would say Now let s repeat with the micro frontend being previewed Stop the myReactMife project s server then run npm run build and then npm run preview The root project will lose the React part due to an incorrect import map as seen in the previous article of the series so to quickly see it again do the same with the root project s server preview it This is the visual result Compare once more The React logo is back Expected since we are now previewing not serving in development mode The React logo is not rotating The logos don t have the expected size The bottom paragraph is written in black not gray The spacing between elements changed The logos in the React side don t have a hover effect The button is still not styled The conclusion that we draw from this exercise During vite serve we get CSS injected but once the project is built no CSS is injected for us We can also conclude that it is best to avoid generic class names or styles for HTML elements in the projects that can unintentionally modify other projects components and HTML elements As a rule of thumb try to always style scoped and minimize the use of general CSS files Optional Peeking Inside the PageIn case you want more validation open the developer tools and look at the HTML node tree Locate and expand the head element You ll see this lt style type text css data vite dev id C Users webJo src myReactMife src App css gt root max width px margin auto padding rem text align center logo height em padding em will change filter transition filter ms logo hover filter drop shadow em cffaa logo react hover filter drop shadow em dafbaa keyframes logo spin from transform rotate deg to transform rotate deg media prefers reduced motion no preference a nth of type logo animation logo spin infinite s linear card padding em read the docs color lt style gt Vite is working its magic It creates code that inserts the styles consumed by components in the form of style elements What you see there is the the exact contents of src App css of the myReactMife project inside the webpage produced by the mySspaRoot project Now that we have identified the problem fully let s work on the solution Mounting and Unmounting CSSHopefully you are familiar with the single spa documentation In said documentation we can see a lot of information There are framework specific tools descriptions of processes to follow and even packages like the single spa css NPM package Since I would like to keep my investigation as neutral as possible in terms of framework I have decided that single spa css is the best choice But oh oh This is a plug in that only plays nice with webpack and we use Vite which is powered by rollup Still this is something that shouldn t be too hard to do on our own Let s program lifecycle functions that mount and unmount CSS CSS Lifecycle FunctionsWe need to modify the file src spa tsx in the myReactMife project to return lifecycle functions for the CSS Allow me to show you the end result since it is quite straightforward import React from react import ReactDOMClient from react dom client ts ignoreimport singleSpaReact from single spa react import App from App let linkEl HTMLLinkElement function bootstrapCss linkEl globalThis document createElement link linkEl rel stylesheet linkEl href import meta env BASE URL assets spa css return Promise resolve function mountCss globalThis document head appendChild linkEl return Promise resolve function unmountCss globalThis document head removeChild linkEl return Promise resolve const lc singleSpaReact React ReactDOMClient rootComponent App errorBoundary err any info any props any return lt div gt Error err lt div gt export const bootstrap bootstrapCss lc bootstrap export const mount mountCss lc mount export const unmount unmountCss lc unmount Super easy task Let s review this We start by declaring the linkEl variable that will hold the reference to the link element we will insert in the document s head element Then we proceed to create bootstrap mount and unmount functions that initialize add and remove the link element to and from the page s head element While the functions are quite simple and straightforward let s highlight a couple of important points here The link s URL It is constructed by concatenating the base URL Vite s base property and the resulting asset file name See a screenshot of the output of npm run build below We simply append what s showing there in magenta color single spa expects the lifecycle functions to return promises so all the lifecycle functions return a resolved promise Ok so let s re build the project and preview it once more Voilá Rotating React logo spacing colors all back But wait the button styling is still wrong What happened If you recall our comparison at the beginning of this article this is an issue while serving and previewing Well the button styles are in the project s src index css file and said file is never imported in any of the bundled JavaScript TypeScript modules This styling existed in the root project before I made the styling changes to it If you recall from the previous article the button was showing proper styling back then We were right Because both projects are so similar we had unintentional coincidental CSS styling across projects I don t know if you know about assets so here it is Assets the files that end up in the assets folder on build are only assets if they are imported The import statements in the JS TS modules is what tells Vite to process them If something is not imported Vite doesn t pick it up doesn t bundle it doesn t parse it for asset URL replacing etc So the lesson here is Always put all micro frontend styles in imported CSS files To quickly see the difference add the statement import index css to src App tsx rebuild and restart previewing You ll see that the size of assets spa css increases and if you refresh the root project s home page you ll see that the button s style is now applied Whether or not you keep a general stylesheet in your micro frontend is up to you Just remember that it needs to be imported somewhere for Vite to pick it up It can t just exist or just be referenced in the micro frontend s index page because the index page is ignored when building the project If you were to ask me I would have a general stylesheet if I had to style the same in several places components Otherwise I would stay in the realm of scoped per component CSS Ok so it seems that we are in the business of making great user interfaces with single spa Let s go back to serving the projects not previewing Stop both Vite servers mySspaRoot and myReactMife and restart serving npm run dev We want to make sure we haven t broken anything in serve mode Refresh the project root s page What do you see All but the React logo right All seems fine including the rotating logo and the button s style Everything is ok or is it Open the browser s console Boom You ll find this Failed to load resource the server responded with a status of Not Found react svg Failed to load resource net ERR NAME NOT RESOLVED spa css The first one is expected We know that while in serve mode we cannot get assets but the second one is new Examine the page s source and locate the end of the contents of the head element to find this lt link rel stylesheet href assets spa css gt We are generating and invalid URL for the stylesheet because we built a URL that starts with two slashes Let s quickly correct that in src spa tsx const base import meta env BASE URL linkEl href base base endsWith assets spa css Refresh the root s page in the browser and open the console We now have a different error GET http localhost assets spa css net ERR ABORTED Not Found spa tsx This is in response to the inserted link element in head lt link rel stylesheet href assets spa css gt The URL we have constructed while now without the double slash problem still points to an incorrect location The server that has the stylesheet is not the one in port The correct port is Furthermore during serve there is no bundle so spa css doesn t really exist while serving This happens because Vite while in serve mode reduces full URL base values to its path It is a manifestation of a problem we have already fully identified Promote a change Visit this GitHub discussion and upvote it if you would like to see Vite serving assets while in serve mode While the presence of this error is not a big deal I would like to explore the possibility of getting rid of this message Enhancing CSS MountingThe problem described just above happens because src spa tsx blindly tries to mount CSS This mounting is actually unnecessary when Vite runs in serve mode We have seen early in this article how Vite s magic inserts all styling for us The solution then is to only mount CSS whenever Vite is not running in serve mode We don t need this work while in serve mode Vite is a bundling tool primarily It is actually not present in the majority of cases after it builds the project The solution then must persist through the building process and must not be dependant on the existence of Vite Ideally I would like to code a simple guard like this function bootstrapCss if vite serve return Promise resolve The rest here The problem s solution is then reduced to find a way to define vite serve As it turns out this is really simple to accomplish Vite has the ability to define constants using its define section in the configuration All we need to do is define this to be true or false depending on the value of the current Vite command Let s tweak Vite s configuration once more using something we have used before We will return a function that returns the configuration object as opposed to returning the configuration object directly This is how vite config ts should look like after our modification import ConfigEnv defineConfig from vite import react from vitejs plugin react import vitePluginSingleSpa from vite plugin single spa export default function opts ConfigEnv return defineConfig plugins react vitePluginSingleSpa type mife serverPort spaEntryPoint src spa tsx server hmr false define vite serve opts command serve true false Now we are exporting a function that receives Vite s configuration environment as first argument Said object contains the command property that tells us if Vite is running in serve or build mode We proceed to use the command property in the definition of the constant we are creating named vite serve Now the problem is solved All we need to do is make use of this constant This is how src spa tsx ends up looking like import React from react import ReactDOMClient from react dom client ts ignoreimport singleSpaReact from single spa react import App from App let linkEl HTMLLinkElement const noCss gt Promise resolve function bootstrapCss linkEl globalThis document createElement link linkEl rel stylesheet const base import meta env BASE URL linkEl href base base endsWith assets spa css return Promise resolve function mountCss globalThis document head appendChild linkEl return Promise resolve function unmountCss globalThis document head removeChild linkEl return Promise resolve const lc singleSpaReact React ReactDOMClient rootComponent App errorBoundary err any info any props any return lt div gt Error err lt div gt export const bootstrap vite serve noCss bootstrapCss lc bootstrap export const mount vite serve noCss mountCss lc mount export const unmount vite serve noCss unmountCss lc unmount As you can see I found it to be more succint to make use of the vite serve constant at the bottom of the module in a ternary conditional operator NOTE For TypeScript projects like the one we are using here we must do one more thing We need to inform TypeScript about this constant We do this by creating the file src env d ts and adding one line declare const vite serve boolean We have reached the end of exercise We now know how to inject CSS and when while working with Vite projects and single spa At this point in the series I have successfully delivered the core promises Vite projects that can be used simultaneously as standalone or single spa micro frontends Vite projects that can serve as root single spa projects Vite single spa projects that can properly serve assets at least after being built Vite single spa projects that load CSS while in serve or build modes Vite root projects that utilize import maps and the import map overrides NPM package With what we have learned up to this point we can start messing around with bigger more complex and varied projects and we can look for opportunities to improve the new vite plugin single spa plug in We will be vigilant of new challenges as we progress with the experimentation Today s learnings certainly pose an interesting question Can CSS injection be handled inside vite plugin single spa After all the plug in can get the CSS file name or names base URL and current Vite command serve or build It feels like the plug in could at least create the CSS lifecycle functions in a separate dynamically created module This sounds more like a rollup task I ll investigate to see if this is possible and will keep you all informed In the meantime enjoy your Vite single spa enabled projects Happy coding	2023-08-13 22:03:26
海外TECH	DEV Community	Complementing exceptions - Introducing monads for error handling in ruby	https://dev.to/cherryramatis/complementing-exceptions-introducing-monads-on-ruby-5fip	Complementing exceptions Introducing monads for error handling in rubyHave you ever considered your approach to handling exceptions I m referring tothe method in which you use the raise keyword within a class and then youutilize the rescue keyword in the function that calls that method However incontemporary programming languages like OCaml Rust Elm Haskell and Go there exists an alternative approach that is contrary to exceptions Essentially errors are treated as values and we manage them as regular variables using constructs like match statements or simple if statements In this article wewill delve into the implementation of this technique using the dry monads gem Table of contentsWhat is the problem with exceptions What are the pros and cons of using errors as valuesPutting our hands to workConclusion What is the problem with exceptions Exceptions can be quite easy to raise when you re just looking at the method you re developing but when you try to consume a library or a method inside your big codebase it s noticeable some annoyances that we ll look right now Does this method trigger an exception Whenever a method is invoked in your codebase or through a third party library there s no immediate certainty regarding whether that function will result in an exception being thrown In the most unfortunate scenario if you haven t referred to the documentation or examined the code to identify any unhandled exceptions a sudden issue arises An unmanaged exception emerges from your application and probably production is down right now Which method triggered that error It s quite common to have a method that consume a lot of other methods if all of those methods trigger different errors it can be very hard to identify which method triggered what while we re developing the method error messages can be helpful but not accurate What are the pros and cons of using errors as values So far I presented to you the pain points of exceptions and introduced a possible solution the dry monad gem but since in the programming field there is no silver bullet it s crucial to understand the pros and cons of every possible solution and that s exactly what we re going to see on this section below ProsThe runtime helps you a little at least Imagine the following scenario you call a function and expect to return a User but that method returns a Error suddenly you can t use user name because ruby will tell you that variable is an error type and not a User leading to easy debugging and preventing future bugs at production Disclaimer This is not as good as having compile time error but the idea here is to improve your current development experience by bringing the exceptions closer to you Deal with error handling before business logic While this might be a more personal preference than a purely technical advantage working with errors as values allows you to explore fully the power of early returns by handling all the unhappy paths at the beginning of your method Clear view of which method returned which error The beauty of dealing with errors as return values becomes evident by the transparency it brings to the codebase As errors are directly returned from methods it becomes clear which error corresponds to which method ConsChallenges while managing deeply nested errors As we presented on previous topics the benefit of linking errors to their original methods a difficulty arises in scenarios where you have a deeply nested method chain in this case it s hard to keep context of where these exceptions passed through Putting our hands to workFirst let s define some disclaimers about dry monads Dry monads is not about avoiding exceptions it s more about using exceptions within a controlled environment where you know you re raising a exception Dry monads are not perfect ruby is a dynamic language and we can t have perfect compile time checks but we can improve our development experience at the best we can Now that we settled our points let s create a sample project to present how to use this new gem Creating the projectYou can create a sample project with mkdir project amp amp cd project amp amp bundle initAnd then add the only dependency of this project dry monads bundle add dry monads How to return an errorInitially we will examine the Result monad If you re familiar with Rust comprehending this concept might be relatively straightforward Essentially the Result monad encapsulates two potential outcomes either a Success value or a Failure error To work with this result monad first we need to require the library and then for convenience include the Dry Monads result so we can use Success and Failure without the module prefixes as showed below require dry monads all class Auth include Dry Monads result param name String return Failure Symbol Success name String def authenticate name return Failure unauthorized unless name correct Success name cherry endendIf we try to call this method expecting to see a name parameter from it like this val Auth new authenticate name incorrect puts val nameYou ll get an error from the ruby runtime ruby main rbmain rb in lt main gt undefined method name for Failure unauthorized Dry Monads Result Failure NoMethodError puts val name Cool right Now the runtime help us understand if a function trigger an erroror not and we can handle it property but how do we get the object inside theFailure on this and log into the console Let s see two approaches for that How to unwrap the Result variants Pattern matchingYou can use the new pattern matching syntax introduced on ruby version to unwrap both variants like below case Auth new authenticate name incorrect in Dry Monads Result Success name String gt user puts userin Dry Monads Result Failure unauthorized gt error puts errorendThis pattern will match on the Failure variant and the output print will be ruby main rb unauthorizedIf you change the name parameter from incorrect to correct you ll have the following output print instead ruby main rb name gt cherry If statementsUsing plain old if statement we ll need to use some new methodsIt s also possible to use the good old if statements the result provide boolean methods and also a bind method to unwrap the variant On the example below we handle it with a plain puts but you can imagine how easy is to use a early return to handle the failure or success variant cases instead value Auth new authenticate name incorrect value bind user puts user if value success value bind error puts error if value failure As you can see we have some methods such as success and failure that return booleans facilitating our life when dealing with control statements Additionally we have the bind designed to unwrap the result variant with a closure Getter methodsAnother way to unwrap a specific variant is to use the correspond getter method this is specially useful when you re already inside a if statement and can be used as follow value Auth new authenticate name incorrect puts The error variant is value failure if value failure puts The success variant is value success if value success Yield syntaxThe yield syntax is a method to unwrap only the Success variant of a result without entering a closure if the method return a Failure the unwrapping will not happen so it s recommended to handle the specific failure cases before using the yield Disclaimer The include statement it s required to use the yield syntax class Runner include Dry Monads Do for call def call value Auth new authenticate name incorrect return value failure if value failure yield value endendputs Result Runner new call Dealing with deep nested errorsAt the beginning of this article I presented a problem with handling errors as values That problem is when you have to return different errors for a deep nested method where a method invokes another and so forth But how do we deal with this problem In languages like Golang a function like errors Wrap exists to facilitate the contextual addition to an error simplifying the identification of the error origin and providing a lot more information besides just a error message Using dry monads we can leverage the full power of ruby dynamic nature by allowing us to return anything inside the Failure variant that way we can create complex data structures like hashes to register context about the error call stack Let s assume the same class we had before but with a tweak on the error handling require dry monads all class Auth include Dry Monads result param name String return Failure error Symbol context String username String Success name String def authenticate name return Failure error unauthorized context Auth authenticate username name unless name correct Success name cherry endendAs you can see we can return an object with some keys that provide more information about that error where it was called and any useful information about it that freedom allow us to create a key like parent ParentClass parent method that essentially mimics the functionality of errors Wrap in the Golang world We can for sure create more complex structures with custom classes but on this article I chose to go with a more simple and straightforward approach to introduce the potential Bonus dealing with the null representationWe saw how to handle failures and success variants for our business logic but maybe you re thinking with yourself I can abstract the absence of value as well and you would be absolute right we can The absence of value can be understand as None and the value itself can be understand as Some dry monads gem provide this amazing functionality for us using the same concepts as we saw with the Result Consider a similar class as we saw above but using the maybe variants instead of the result ones require dry monads all class Auth include Dry Monads maybe param name String return None Some name String def authenticate name return None unless name correct Some name cherry endendnone val Auth new authenticate name incorrect some val Auth new authenticate name correct puts None gt none val puts Some gt some val With this sample code our output will be the following ruby main rbNone gt NoneSome gt Some name gt cherry Similar to the Result monad we can do pretty much every control statement as previously showed below we ll see all of them briefly Pattern matchingrequire dry monads all class Auth include Dry Monads maybe param name String return None Some name String def authenticate name return None unless name correct Some name cherry endendcase Auth new authenticate name correct in Dry Monads Maybe None puts None branch in Dry Monads Maybe Some name String gt user puts Some branch user end If statementsrequire dry monads all class Auth include Dry Monads maybe param name String return None Some name String def authenticate name return None unless name correct Some name cherry endendoption Auth new authenticate name incorrect puts This is the none option if option none option bind opt puts This is the some option opt if option some It s important to observe that we don t need to use the bind method on None because this variant will just represent the nothingness of value Yield syntaxDifferently than the Result monad Maybe don t provide us a getter method so we need to rely on the yield syntax when we don t want to use a closure like on bind class Runner include Dry Monads Do for call include Dry Monads maybe def call option Auth new get user name id return None if option none yield option endendputs Result Runner new call Similar to the Result yield just work on the happy paths in this case the Some variant ConclusionAs always I hope you liked this article and learned something new I m working on a new gem to wrapping exceptions and returning this monads I hope to get something working soon and writing the part of this article May the force be with you	2023-08-13 22:03:04
ニュース	BBC News - Home	Zuckerberg says Musk 'not serious' about cage fight	https://www.bbc.co.uk/news/business-66494113?at_medium=RSS&at_campaign=KARANGA	billionaires	2023-08-13 22:28:02
ニュース	BBC News - Home	Moises Caicedo transfer news: Chelsea agree £115m deal for Brighton midfielder	https://www.bbc.co.uk/sport/football/66491106?at_medium=RSS&at_campaign=KARANGA	british	2023-08-13 22:09:18
ニュース	BBC News - Home	Moises Caicedo: Why Chelsea and Liverpool both wanted Brighton midfielder	https://www.bbc.co.uk/sport/football/66493086?at_medium=RSS&at_campaign=KARANGA	Moises Caicedo Why Chelsea and Liverpool both wanted Brighton midfielderMOTD pundit Danny Murphy says Chelsea s draw with Liverpool shows why both wanted Brighton s Moises Caicedo before the Blues got their man	2023-08-13 22:20:34
ニュース	BBC News - Home	Match of the Day 2: Pochettino brings 'full throttle' football to Chelsea	https://www.bbc.co.uk/sport/av/football/66494669?at_medium=RSS&at_campaign=KARANGA	Match of the Day Pochettino brings x full throttle x football to ChelseaMatch of the Day s Shay Given praises Chelsea s new full throttle style of play under Mauricio Pochettino following their draw with Liverpool	2023-08-13 22:34:58
ビジネス	ダイヤモンド・オンライン - 新着記事	【どうする家康】「重要人物」消したデタラメな脚本、秀吉の“お市への恋愛感情”の真偽は？ - ニュース3面鏡	https://diamond.jp/articles/-/327585	【どうする家康】「重要人物」消したデタラメな脚本、秀吉の“お市への恋愛感情の真偽はニュース面鏡先週放送の「どうする家康」では、家康が堺見物をしている間に本能寺の変が起こり、忍者たちの助けでようやく岡崎に逃げ帰った。	2023-08-14 07:30:00
ビジネス	ダイヤモンド・オンライン - 新着記事	自動運転車に半信半疑、米テック先進都市の実情 - WSJ発	https://diamond.jp/articles/-/327634	半信半疑	2023-08-14 07:19:00
ビジネス	東洋経済オンライン	高すぎる日米の｢株価崩壊｣がゆっくり進んでいる 今後の日経平均株価は下落加速の局面を警戒 | 市場観測 | 東洋経済オンライン	https://toyokeizai.net/articles/-/694269?utm_source=rss&utm_medium=http&utm_campaign=link_back	終値ベース	2023-08-14 07:30:00
IT	IT号外	X(旧Twitter)のフォローしている人のアカウントの過去ツイートが見れなくなってる？下へスクロールできない時に試してみること	https://figreen.org/it/x%e6%97%a7twitter%e3%81%ae%e3%83%95%e3%82%a9%e3%83%ad%e3%83%bc%e3%81%97%e3%81%a6%e3%81%84%e3%82%8b%e4%ba%ba%e3%81%ae%e3%82%a2%e3%82%ab%e3%82%a6%e3%83%b3%e3%83%88%e3%81%ae%e9%81%8e%e5%8e%bb%e3%83%84/	X旧Twitterのフォローしている人のアカウントの過去ツイートが見れなくなってる下へスクロールできない時に試してみることびわ湖の花火大会が、高いフェンスを立てて目隠しをして、お金を払わない人達に花火を見せないというニュースが取り上げられてましたね。	2023-08-13 22:11:19