firewall-objects 0.1.3

Firewall object primitives for networks, services, and application indicators.
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43

# Changelog

All notable changes to this project will be documented in this file. The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/).

## [0.1.0] - 2026-01-19

### Added

- Initial release covering network primitives (hosts, CIDRs, ranges, FQDNs).
- Transport services with well-known registry and parsing helpers.
- Application indicators and sample catalog entries.
- Optional JSON-enabled object store with CRUD operations.
- Integration tests demonstrating combined workflows.

## [0.1.1] - 2026-01-20

### Fixed

- Removed `serde` derives from `ApplicationDefinition`/`ApplicationIndicators` so Clippy succeeds (they use borrowed slices that aren’t
  deserializable). Serialization remains available via `ApplicationObj`.
- Ran clippy fix to collapse multiple nested if blocks in src/service/application/mod.rs -> Lines(82:9, 92:9, 102:9, 120:9, 131:9, 141:9)

## Bugfix - 2026-01-20

- Fqdn rejects numeric TLD when parsing with FQDN::new("host.domain.123") src/ip/fqdn.rs:65-71
- Add module level test src/ip/fqdn/tests/rejects_numeric_top_level_domain:124-130

### Documentation
- Comprehensive README with usage examples and feature overview.
- Module-level documentation throughout the crate.

## [0.1.3] - 2026-01-28
- Introduced a full builder module (src/builder.rs:1) that lets you declare objects in the
  “dotted” style: address("server1", "192.168.50.10"), service::tcp(12849), fluent network_group/
  service_group chaining, and an application() builder for DNS/TLS/HTTP hints. Everything funnels
  into the shared BuilderEntry, so the doc-tested example at the top of the file demonstrates how to
  add a mix of addresses and service groups directly into an ObjectStore.
- Extended the store itself (src/objects/mod.rs:3 and especially src/objects/mod.rs:130) so
  ObjectStore::add accepts anything that implements Into<BuilderEntry>—network/service objects,
  their respective groups, or the new application builder output—making the sample loop you
  described compile cleanly.
- Added coverage that mirrors the intended workflow (tests/integration.rs:124 and tests/
  integration.rs:160), using the network/service builder flow and the application builder.