Search results for 'framework'

Osm Framework introduced JS controllers, and JS unit tests. osmcommerce.com website project was renamed to osm.software, it finalized the post rendering, and introduced a tool for checking broken links.

Osm Framework introduced production mode and maintenance mode. osm.software website went live.

Yesterday, I tested the instructions for installing Osm Admin locally as a contributor.

I waited for this day too long. Today, I've tried out GitPod, and made it work for a project based on Osm Admin.

After getting the main branch all-green (tests pass, CLI and UI works as expected), I decided that from now on, I'll keep it always green, and use feature branches for all major development.

Then, I started implementing the main menu of the admin area.

Before diving into what should be in the docs, let's define what you should more or less know before using Osm Admin.

There are four types of people who will read the docs: power users, developers, vendors and contributors.

Yesterday:

• Osm Admin in-browser functionality was fully restored after creating search index in the indexer.
• All test suites started passing again, and being run automatically on git push.

After enumerating what kind of changes can happen to a property, I started implementing the most hard one - changing property type.