Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Rename with_defaults to tag_defaults #552

Merged
merged 3 commits into from
Oct 23, 2020
Merged

Rename with_defaults to tag_defaults #552

merged 3 commits into from
Oct 23, 2020

Conversation

stephendolan
Copy link
Member

This PR aims to close #548

It will need to be released in conjunction with luckyframework/lucky#1262

This PR tackles:

  • Renaming with_defaults in browser_app_skeleton/src/components/shared/field.cr to the new tag_defaults signature implemented here
  • Renaming the yielded block from input_builder to tag_builder to keep all Lucky-generated docs/code/comments consistent and (hopefully) better convey meaning

I wasn't sure how to get the specs passing here since the method won't be found in Lucky until a new version is available.

This PR aims to close #548

This PR tackles:
- Renaming with_defaults in `browser_app_skeleton/src/components/shared/field.cr` to the new `tag_defaults` signature implemented [here](luckyframework/lucky#1262)
- Renaming the yielded block from `input_builder` to `tag_builder` to keep all Lucky-generated docs/code/comments consistent and (hopefully) better convey meaning
Copy link
Member

@jwoertink jwoertink left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This will be fine. Obviously we will need to update the Lucky version. To get the specs to pass, we can now update https://github.com/luckyframework/lucky_cli/blob/master/shard.override.yml to point to lucky master. Once the other PR is merged in, we can rerun specs here and they will be good.

@stephendolan
Copy link
Member Author

@jwoertink Sorry, somehow I missed your comment. Do you want me to go ahead and update shard.override.yml in this PR?

@jwoertink
Copy link
Member

@stephendolan yeah, it's a pretty common thing we end up having to do so it's fine. Update it to point to lucky master, and we will see if the specs all pass.

Copy link
Member

@jwoertink jwoertink left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Change Shared::Field to use tag_defaults and yield tag_builder
2 participants