bulma_x 0.2.0

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA256:
+  metadata.gz: 823e9fe9d30593327aa0d49f02099f41d96c1dc3ef9b86cf29f2f82d935d9ffc
+  data.tar.gz: cbfdbcb1ff2ac540069970e1914c554fbcd049a96d81ff9281fb4155bcf6ebfe
+SHA512:
+  metadata.gz: be69706ce1d08b5b74367539cba02efc0b218647c0853123dd91ad444e3d9c5f373fd20253b87e314cbba092a2a1d182f1fdc01a657f7a540c2a897841f60ae6
+  data.tar.gz: d3fa32758ed942c806019069f235e53c581a776a63b1aa37b7052e7d9c7cba063e2f38ecf702c1b20c7e887eac36a9e1c48a58cd04dbe45a23d8c03748fb6d14

data/.rspec

@@ -0,0 +1,3 @@
+--format documentation
+--color
+--require spec_helper

data/.rubocop.yml

@@ -0,0 +1,22 @@
+AllCops:
+  TargetRubyVersion: 3.4
+  NewCops: enable
+
+# Until we develop the automated documentation tool, we disable this cop
+Style/Documentation:
+  Enabled: false
+
+Metrics/MethodLength:
+  Max: 20
+
+Metrics/BlockLength:
+  Max: 20
+  Exclude:
+    - 'spec/**/*_spec.rb'
+    - 'spec/support/matchers/*.rb'
+    - 'spec/support/shared_examples/*.rb'
+    - '*.gemspec'
+
+Layout/LineLength:
+  AllowedPatterns:
+    - '^\s*#'

data/CHANGELOG.md

@@ -0,0 +1,30 @@
+# Changelog
+
+<a name="0.2.0"></a>
+## 0.2.0 (2025-05-15)
+
+### Added
+
+- ✨ Makes method slot private [2d54a12]
+- ✨ Columns is now deferred [d9a4fd1]
+- ✅ Fixes all specs now that all components (except Pagination) are deferred [895b8f8]
+
+### Changed
+
+- 🚨 Configure rubocop and remove remaining warnings [f0ffa25]
+- 🔧 Adds .gitlab/issue_templates [1c11235]
+
+### Miscellaneous
+
+- 📝 Add Features and Non-Features sections in README [208618d]
+- 📝 Add contribution rules [880cc1c]
+- 🚧 First pass with vanilla rubocop [fd1b395]
+- 📝 Updates README with a quick overview of the project [81b058a]
+- 🚧 Adds GlobalOption extra_classes and makes all component deferred [ffc944e]
+- 🔀 Merge branch migrate_components_to_deferred_rendering into master [81f3dd8]
+
+
+<a name="0.1.0"></a>
+## 0.1.0 (2025-05-06)
+
+- 🎉 Initial release

data/CONTRIBUTING.md

@@ -0,0 +1,50 @@
+# Contributing
+
+Thank you for considering contributing to BulmaX
+
+You can contribute in the following ways:
+
+- Finding and reporting bugs
+- Contributing code to BulmaX by fixing bugs or implementing features
+- Improving/Writing the documentation
+
+## Bug Reports
+
+Bug reports and feature suggestions must use descriptive and concise titles and be submitted via Gitlab Issues. Please use the search function to make sure that you are not submitting duplicates, and that a similar report or request has not already been resolved or rejected.
+
+## Submitting Code Changes
+
+### Features
+
+Please do not work on major features and ideas without first creating an issue for discussion. We are a tiny team, and are unlikely to be able to pick these up as quickly as you might prefer.
+
+### Smaller Fixes
+
+If you are fixing a bug, please open a merge request (MR). Ensure that your changes include passing tests, adhere to our coding style, and that the MR references the issue it resolves.
+
+### Testing
+
+New features should also ideally come with additional tests to ensure they work as expected, and don't break existing code.
+
+## Merge Requests
+
+### Size and Scope
+
+Our time is limited and MRs making large, unsolicited changes are unlikely to get a response. Changes which link to an existing confirmed issue, or which come from a "help wanted" issue or other request are more likely to be reviewed.
+
+The smaller and more narrowly focused the changes in a MR are, the easier they are to review and potentially merge. If the change only makes sense in some larger context of future ongoing work, note that in the description, but still aim to keep each distinct MR to a "smallest viable change" chunk of work.
+
+### Description of Changes
+
+We are using [Gitmoji](https://gitmoji.dev/) style for commit messages and every MR is expected to have [git atomic commits](https://www.aleksandrhovhannisyan.com/blog/atomic-git-commits/) as much as possible.
+
+> Using emojis on commit messages provides an easy way of identifying the purpose or intention of a commit with only looking at the emojis used.
+
+Commit messages are expected to have a descriptive title, starting by a verb like "Add", "Change", "Deprecate", "Remove", or "Fix".
+
+### Technical Requirements
+
+Pull requests that do not pass automated checks on CI may not be reviewed. In particular, please keep in mind:
+
+- Testing (rspec)
+- Code style rules (rubocop)