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

Seal auto-populate #39

Open
ataran opened this issue May 5, 2014 · 8 comments
Open

Seal auto-populate #39

ataran opened this issue May 5, 2014 · 8 comments

Comments

@ataran
Copy link

ataran commented May 5, 2014

Related to #30
The seal process flow is such that:

  1. User wants to seal an attribute
  2. User sets junk seal value
  3. User compiles
  4. User reads compilation error and gets seal value from message
  5. User updates code to reflect correct seal based on the code listed during compilation error message
  6. User compiles
  7. END if compilation successful, go to 4 if build fails

IMHO the fact that a compilation must fail in order for user to obtain the seal value, is counterproductive.

I understand the value of seals as a protection measure when a sealed code segment is being updated, but if a new attribute or previously not sealed attribute is being sealed, I think there should be a shortcut to auto-populate the seal during compilation without having to read the error message, getting the value, updating the code & recompiling.

@ataran
Copy link
Author

ataran commented May 5, 2014

so i guess i'm suggesting a command or a shortcut that could be used to auto-populate a seal if the statement is net new or not currently sealed

@davvd
Copy link

davvd commented May 7, 2014

I'll ask someone to take care of this task soon

@davvd
Copy link

davvd commented May 7, 2014

@ataran thanks for the ticket, your account was topped for 15 mins, payment 39307426

@davvd
Copy link

davvd commented May 25, 2014

@yegor256 it's yours now, please proceed keeping in mind our principles. Feel free to ask any technical questions right here in the ticket

@davvd
Copy link

davvd commented May 25, 2014

@yegor256 This task's budget is 30 mins. This is exactly how much will be paid when the problem explained above is solved. See this for more information

@yegor256
Copy link
Owner

@davvd assign someone else pls

@davvd
Copy link

davvd commented Sep 28, 2015

@davvd assign someone else pls

@yegor256 30 points was deducted from your rating

@davvd
Copy link

davvd commented Sep 28, 2015

@davvd assign someone else pls

@yegor256 got it, someone else will be assigned soon

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

No branches or pull requests

3 participants