Ruby style guide VS CIPs

By default, RuboCop will enforce the style defined in the Ruby Community Style Guide. We can tailor it to our specific tastes and context, but let's rely on this basic set of rules to learn how to use RuboCop.

RuboCop is a Ruby static code analyzer (a.k.a. linter) and code formatter. Out of the box it will enforce many of the guidelines outlined in the community Ruby Style Guide. Apart from reporting the problems discovered in your code, RuboCop can also automatically fix many of them for you.

Read more about Ruby.

8. Use a consistent style: Consistency is key when it comes to writing readable code. Use a consistent style throughout your codebase, and follow common Ruby style guides like Ruby Style Guide.

The real standard is to use default rubocop configuration which is based on https://rubystyle.guide/.

It used to, before recently. It literally said, "The and and or keywords are banned."

rubocop/ruby-style-guide

As you see - there are no reference to any technology or framework. There are a lot of best-practices for almost any framework, so you can choose an appropriate one. For example - if you're a rails developer, then you can check https://github.com/rubocop/ruby-style-guide and https://github.com/rubocop/rails-style-guide but if you're a golang developer - https://github.com/uber-go/guide/blob/master/style.md and https://developers.mattermost.com/contribute/more-info/server/style-guide/

CPS-???? | Governance Security [New Problem]: This problem statement describes security issues to be considered by protocol governance CIPs.

The Lace team is already working with the community on how to find the best way to develop the CIP-72 - DApp Registration & Discovery. If you’re interested in taking part, contribute here

All mobile wallets have some kind of dApp browser, but there are no hard specs for how they should be run that is implemented at the moment. You might be interested in CIP72 if you're interested in standards for this topic more generally: https://github.com/cardano-foundation/CIPs/pull/355

CIP-???? | Extend token metadata for translations [New Proposal]: This proposal defines an addition to CIP-25 | Media NFT Metadata Standard to support more languages than English.

If you wish to add your perspectives to CIP 1694, make sure to share them here. Add your voice as the era of Voltaire rolls out!

Last week, a community-led roundtable took place on the topic of CIP-1694. You can catch the recap and outcome in last week’s newsletter or this Cardano Forum recap here. Worth a read.

Conditions inside a native script (but there is a CIP for changing this here)

Thank you for the information! That is very important. Actually I wrote a specification https://github.com/cardano-foundation/CIPs/pull/442 where I address exactly that issue.